Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2001-02

FTP - down ?

24 messages · 12 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael Van Canneyt
to Curtis White: I don't think that lowercase is a requirement for the Unices. Unix/Linux can handle most…
Curtis White wrote 18 lines
SVAA wrote: > > Hello: > > I'm working on saving and loading units and projects, and I've got some > doubts: > a) Files should always be saved in lowercase to avoid Unices troubles �isn't > it? I don't think that lowercase is a requirement for the Unices. Unix/Linux can handle most any filename that Windows can. Since a lot of work is done from the command line in the Unices, it is typically frowned on to use spaces and uppercase letters because they are hard to type. To use spaces in filenames, you have to enclose the name in quotes. I don't think it would be a good idea to restrict the users strictly to lowercase filenames or filenames without spaces. These things should be allowed and then leave it up to the developer to determine if he wants to make all Unix users mad or not :-)

The problem is actually deeper than that: The compiler ONLY looks for lowercase units, so you better force lowercase.

With Kylix coming up, Peter Vreman is going to change this behaviour. I believe the behaviour will be the following:
- Look for lowercase unit source, as it is now.
- Look for unit with casing as in uses clause.
(- on dos: look for uppercase units)
The order in which this will be done is not yet clear: Look in all directories for the lowercase version and then in all directories for the original casing, or look in all directories for the lowercase or 'original case' unit.

It is actually an interesting problem, since Pascal syntax is case insensitive. So the unit clause should also be case insensitive, but Borland (Kylix) decided that the units are saved with upper/lowercase preserved, which is strictly speaking a violation of the case-insensitiveness...

Michael.

Reply by email

SVAA

Hello:

I'm working on saving and loading units and projects, and I've got some doubts:
a) Files should always be saved in lowercase to avoid Unices troubles �isn't it?
b) What is 'aliases' property of Tproject for?
c) What is TargetFileExt property for?

Reply by email

Curtis White
to SVAA
SVAA wrote 7 lines
Hello: I'm working on saving and loading units and projects, and I've got some doubts: a) Files should always be saved in lowercase to avoid Unices troubles �isn't it?

I don't think that lowercase is a requirement for the Unices. Unix/Linux can handle most any filename that Windows can. Since a lot of work is done from the command line in the Unices, it is typically frowned on to use spaces and uppercase letters because they are hard to type. To use spaces in filenames, you have to enclose the name in quotes. I don't think it would be a good idea to restrict the users strictly to lowercase filenames or filenames without spaces. These things should be allowed and then leave it up to the developer to determine if he wants to make all Unix users mad or not :-)

b) What is 'aliases' property of Tproject for?

This was designed to hold the unit aliases like those in Delphi. In other words, if you have a unit called "linux" and it is later renamed to "linapi", then you could put in an alias of "linux=linapi" so the IDE can substitute linapi whenever it sees linux in the uses clause. The aliases would likely be separated by semi-colons (;), or something similar, as they are in Delphi.

c) What is TargetFileExt property for?

This was meant to be the same as in Delphi. Basically, it is the file extension to be used for the target executable file.

Curtis

Reply by email

Unknown author
to Unknown author: I think we should NOT support this. Stefan -----------------------------------------------…
Show quoted text 9 lines
On Wed, Feb 28, 2001 at 07:49:00AM +0000, Curtis White wrote: > [.. aliases ..] > But Lazarus could support it if we want to. We could just replace one > with the other in the source code before submitting it to the compiler. > I guess that is something we need to decide (if we want to support > aliases or not within Lazarus). If not, then we can remove that property > from the TProject class. I think we should NOT support this.

I also think so. This is a leftover from Delphi 1 to support old TPW code, I don't see why it should find it's way into more up-to day environments.

I would drop it.

Michael.

Reply by email

Mattias Gaertner
to Peter Vreman: ID> E This is not supported by the compiler. And it won't be supported in the future as…
Show quoted text 10 lines
On Wed, Feb 28, 2001 at 07:49:00AM +0000, Curtis White wrote: > [.. aliases ..] > But Lazarus could support it if we want to. We could just replace one > with the other in the source code before submitting it to the compiler. > I guess that is something we need to decide (if we want to support > aliases or not within Lazarus). If not, then we can remove that property > from the TProject class. I think we should NOT support this.

I think it is an atavism and I will not support it.

Mattias

Reply by email

Shane Miller

I am looking at the GTK side of things trying to find bugs and stuff. I'm not directly touching the IDE.

Shane

>> 02/28/01 02:24AM >>>

Hi all,

Just want to get an overwiev: Who is currently working on what part of the IDE?

Mattias

I'm working on saving and loading units and projects, and I've got some doubts:

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Peter Vreman
Show quoted text 5 lines
Hello: I'm working on saving and loading units and projects, and I've got some doubts: a) Files should always be saved in lowercase to avoid Unices troubles

�> isn't

it?

The 1.1 compiler supports also case sensitive names (to be compatible with Kylix). But first is looked for the lowercase name to be backwards compatible.

Reply by email

Unknown author
to SVAA: Hello: I'm working on saving and loading units and projects, and I've got some doubts: a)…

Hi

On Thu, Mar 01, 2001 at 07:28:06PM +0000, Curtis White wrote: [... MessagDlgStuff...]

Most definitely. Can you just send them to me please?

I just had a second look at the stuff and it seems to be easy to commit directly to cvs. So I'll do that tonight.

The following stuff will be included:

- the internal class TMessageBox
(which will be used from the functions below)
- the well known functions from the delphi dialogs unit (ShowMessage, MessageDlg ...)
- some simple bitmaps (warning stuff...)
- an example program

- The different buttons (ok, abort, ..) are already there and nearly all are working

Whats left to do:

- The calculation of textwidth is not yet OK (no automatic linebreaks, not yet calculating with the right font)
- The bitmaps should be converted to resources

bye,

Stefan

--------------------------------------------------------- Stefan Hille email: 48155 Muenster voice: 0251/664695

Reply by email

Peter Vreman
Show quoted text 5 lines
> b) What is 'aliases' property of Tproject for? This was designed to hold the unit aliases like those in Delphi. In other words, if you have a unit called "linux" and it is later renamed to "linapi", then you could put in an alias of "linux=linapi" so the

ID> E

can substitute linapi whenever it sees linux in the uses clause. The aliases would likely be separated by semi-colons (;), or something similar, as they are in Delphi.

This is not supported by the compiler. And it won't be supported in the future as Michael and Florian are against it, because it's only confusing.

It was added in the past in Delphi to allow backwards compatibility of the windows unit with the wintypes and winproc units.

Reply by email

Unknown author
to Peter Vreman
Curtis White wrote 6 lines
[.. aliases ..] But Lazarus could support it if we want to. We could just replace one with the other in the source code before submitting it to the compiler. I guess that is something we need to decide (if we want to support aliases or not within Lazarus). If not, then we can remove that property from the TProject class.

I think we should NOT support this.

bye,

Stefan

--------------------------------------------------------- Stefan Hille email: 48155 Muenster voice: 0251/664695

Reply by email

Curtis White
to Peter Vreman: ID> E This is not supported by the compiler. And it won't be supported in the future as…
Peter Vreman wrote 17 lines
> > b) What is 'aliases' property of Tproject for? > > This was designed to hold the unit aliases like those in Delphi. In > other words, if you have a unit called "linux" and it is later renamed > to "linapi", then you could put in an alias of "linux=linapi" so the ID> E > can substitute linapi whenever it sees linux in the uses clause. The > aliases would likely be separated by semi-colons (;), or something > similar, as they are in Delphi. This is not supported by the compiler. And it won't be supported in the future as Michael and Florian are against it, because it's only confusing. It was added in the past in Delphi to allow backwards compatibility of the windows unit with the wintypes and winproc units.

But Lazarus could support it if we want to. We could just replace one with the other in the source code before submitting it to the compiler. I guess that is something we need to decide (if we want to support aliases or not within Lazarus). If not, then we can remove that property from the TProject class.

Curtis

Reply by email

Curtis White
to Peter Vreman: ID> E This is not supported by the compiler. And it won't be supported in the future as…

Got it boss. It's done.

Curtis

"Michael A. Hess" wrote 16 lines
Curtis White wrote: > > > > > b) What is 'aliases' property of Tproject for? > If not, then we can remove that property from the TProject class. Executive decisions Curtis. Remove it. -- ==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Mattias Gaertner
to SVAA: Hello: I'm working on saving and loading units and projects, and I've got some doubts: a)…

I'm currently working on the project support. There will be a lot of changes to main.pp, uniteditor.pp and project.pp. I will commit tomorrow. After that I will give a list of ToDos.

But there is one thing you could start today: MessageDlg.

Mattias

Show quoted text 6 lines
Removing the Aliases property from TProject. Other than that 1 minute job, nothing. I need to look at it and see what all needs to be done. I don't know exactly what to work on right off. I know that a lot still needs to be done, but I'm just not sure what that "a lot" is. Any suggestions?

Reply by email

Curtis White
to SVAA: Hello: I'm working on saving and loading units and projects, and I've got some doubts: a)…

Removing the Aliases property from TProject. Other than that 1 minute job, nothing.

I need to look at it and see what all needs to be done. I don't know exactly what to work on right off. I know that a lot still needs to be done, but I'm just not sure what that "a lot" is. Any suggestions?

Curtis

Mattias Gaertner wrote 12 lines
Hi all, Just want to get an overwiev: Who is currently working on what part of the IDE? Mattias On 2001.02.28 07:14:05 +0100 SVAA wrote: > I'm working on saving and loading units and projects, and I've got some > doubts:

Reply by email

Marco van de Voort
to Curtis White: But Lazarus could support it if we want to. We could just replace one with the other in…

y> > This is not supported by the compiler. And it won't be supported in the future as Michael

Show quoted text 11 lines
> and Florian are against it, because it's only confusing. > > It was added in the past in Delphi to allow backwards compatibility of the windows unit > with the wintypes and winproc units. > But Lazarus could support it if we want to. We could just replace one with the other in the source code before submitting it to the compiler. I guess that is something we need to decide (if we want to support aliases or not within Lazarus). If not, then we can remove that property from the TProject class.

No, since it can still be in uses clauses in the sources (at least under Delphi), or in the already compiled parts.

Reply by email

Curtis White
to SVAA: Hello: I'm working on saving and loading units and projects, and I've got some doubts: a)…

OK. I can create the MessageDlg. I will start working on that tonight after work.

Curtis

Mattias Gaertner wrote 17 lines
I'm currently working on the project support. There will be a lot of changes to main.pp, uniteditor.pp and project.pp. I will commit tomorrow. After that I will give a list of ToDos. But there is one thing you could start today: MessageDlg. Mattias On 2001.02.28 20:37:41 +0100 Curtis White wrote: > Removing the Aliases property from TProject. Other than that 1 minute > job, nothing. > > I need to look at it and see what all needs to be done. I don't know > exactly what to work on right off. I know that a lot still needs to be > done, but I'm just not sure what that "a lot" is. Any suggestions?

Reply by email